<html>
<head><meta charset="utf-8"><title>PathBuf capacity-related stabilization · t-libs · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/index.html">t-libs</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/PathBuf.20capacity-related.20stabilization.html">PathBuf capacity-related stabilization</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="193384947"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/PathBuf%20capacity-related%20stabilization/near/193384947" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/PathBuf.20capacity-related.20stabilization.html#193384947">(Apr 08 2020 at 22:12)</a>:</h4>
<p>kornelski asked on GitHub about stabilizing the PathBuf methods, and I agree that there's not really any reason not to do so. Would someone on libs be up for reviewing and kicking off FCP on the tracking issue (<a href="https://github.com/rust-lang/rust/issues/58234" title="https://github.com/rust-lang/rust/issues/58234">#58234</a>)?</p>
<p>I think we should hold off on stabilizing shrink_to though since that's tracked by <a href="https://github.com/rust-lang/rust/issues/56431" title="https://github.com/rust-lang/rust/issues/56431">#56431</a>.</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>